-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Created an entry-point for rqt_topic in setup.py #16
Conversation
Signed-off-by: ahcorde <[email protected]>
Please keep the changes in a pull request focused on one semantic change described in the title. If necessary create multiple PRs for orthogonal changes. |
I agree with @dirk-thomas, The fix for the connected issue is adding the entry point (and maybe the Also, please update the title to relate to the fix. |
ae51e31
to
18b296f
Compare
Signed-off-by: ahcorde <[email protected]>
Moved to another PR version and license changes #17 |
Please update the PR title; this package is already an ament_python package. |
@jacobperron @ahcorde I'm looking to release this for the upcoming galactic fork from rolling, seems like this should get in? So friendly bump :) |
Signed-off-by: Scott K Logan <[email protected]>
Signed-off-by: Scott K Logan <[email protected]>
@ros-pull-request-builder retest this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this drops the rqt_topic
command from /opt/ros/foo/bin
, but I think this is actually the right thing to do. A change, nonetheless.
Fixed package to run with
ros2 run rqt_topic rqt_topic
. Related to this issue ros-visualization/rqt_console#20Signed-off-by: ahcorde [email protected]